DRAFT: proposed changes for v2 schema #160
Conversation
schema/v1.1.0/common.yaml
Outdated
| descriptive_name: degrees | ||
| symbol: ° | ||
|
|
||
| alignment_local_alignment_file: |
There was a problem hiding this comment.
Should we have a https and an s3 path to this?
There was a problem hiding this comment.
Honestly, I'm not sure if we even want this field at all - we decided to keep all of the alignment data directly in the db rather than relying on files in s3 for alignment data cc @uermel ?
schema/v1.1.0/api_models.yaml
Outdated
| per_section_parameters: | ||
| range: PerSectionParameters | ||
| inverse: PerSectionParameters.frames | ||
| multivalued: true |
There was a problem hiding this comment.
Should the relationship between the frame and per-section parameters be 1:1?
There was a problem hiding this comment.
each per-section parameters would map to a frame entry thru tiltseries and z-section
There was a problem hiding this comment.
Frames can (at least technically) have multiple per-section-parameters, one for each tiltseries.
schema/v1.1.0/api_models.yaml
Outdated
| tilt_offset: | ||
| exact_mappings: | ||
| - cdp-common:alignment_tilt_offset | ||
| local_alignment_file: |
There was a problem hiding this comment.
I believe this is different from the actual alignment. If that is a correct assumption, should we also add fields to capture the file path to the alignment file?
jgadling
force-pushed
the
jgadling/api-schema-v2
branch
from
7821437
to
bf7c59a
Compare
jgadling
force-pushed
the
jgadling/api-schema-v2
branch
from
bf7c59a
to
039c043
Compare
This is a draft of the schema changes that are coming for the v2 api